BBS Toolkit/BBS Toolkit.iso/pc_board/pcbv421.zip/HISTORY.DOC

Text File | 1992-04-25 | 6KB | 150 lines

PCBVERIFY 4.0x HISTORY
----------------------

-- 4.21 --

Corrected a bug which was preventing long distance numbers from being added
to PCBVVER after the first attempt when set up to do so in PCBV.CNF.

-- 4.20 --

Got rid of the BRUN reuirement.

Fixed a problem with (LDS) and (LOC) sometimes showing up incorrectly in the
logs and on the screen.  Calls were being handled properly but were being
reported as (LOC) even if they were (LDS), if the PCBVAL file contained a
single ? in the long distance (entered) flag field instead of a ?Y.

Also took care of a problem where numbers not found in the PCBVAL file at all
would sometimes be displayed to the user as (Long Distance) even though they
said (Local).

-- 4.10 --

Fixed another problem where PCBVerify would loop on a @ appended to an @X code.
Also fixed the WELCOME file which was distributed with PCBV409 and had this
very problem.

Fixed a problem where PCBVerify would overwrite the last entry in the log file.
This resulted in the disappearance of the line "Opened Door (Verify)" on
PCBoard systems.

-- 4.09 --

Fixed a problem in local mode which would yield an "invalid comport specified"
regardless of the comport setting.  This problem only occurred with local mode.

Fixed a problem with a single @ on a line, or one that was misplaced.  PCBV
would loop infinitely printing the "@".

Fixed a problem PCBV.SYS and PCB12/14 (PCBOARD.SYS file only) systems not
giving the proper time remaining.  This occurred only with non-PCBoard
systems.

Fixed a problem where the expiration date was not properly being adjusted
when using "+days" in the expire date adjust field.

Fixed a few ommissions from the logfile.  Also fixed code which prints user's
phone number on the status line after being entered (or after callerid detect).

-- 4.08 --

Fixed a problem which would case PCBVerify to falsely detect MODEM RING
INDICATE on some systems.  This error was caused by some mods made in
version 4.07.

-- 4.07 --

Whoops!  4.06 did not completely fix the problem with strange comports.
If the leading 0 was included in the comport address, the configuration
routine would strip out the : and mess everything up.  You should no
longer get "invalid comport" messages.  (Sorry about that one -- I thought
I had it fixed.  I don't have non-std comports over here, so I had no idea
it was burping on that).

Fixed a problem with DOOR.SYS systems where COM0 (local) would be returned as
an invalid comport specification.

Made the color @ code drivers more tolerant -- lowercase letters would produce
errors.  Fixed.

Made error messages a little neater in appearance on screen and in the
Verify.err file.  English text should appear for most error messages.

Clarified some contradictions in the documentation regarding error and
non-error dial strings.

-- 4.06 --

Fixed a problem with non-standard comports.  If you entered the aaaa:i
designation for your comport, PCBVerify would simply drop back to DOS.
This has been fixed and PCBVerify will now accept comport addr's in the
format [hex address]:[irq], i.e. 03f8:4, 02e8:5, 0380:4, etc.

-- 4.05 --

Another bug was recently uncovered on my system.  Error correcting modems
were not properly being picked up as so and as a result were calling error-
correcting modems using the non-error-correcting dial string.  Fixed.

-- 4.04 --

Fixed a problem with REVERIFY mode.  PCBVerify would allow numbers to be
reverified even if they were added to PCBVVER because of being long distance
and failed on the first attempt.  PCBVerify now scans the date/comment field
for the string "(ld)" or "(LD)" and if found will not allow the phone number.
Otherwise, it will allow reverification of the number provided the user is
at new user level and the names match.

This of course applies only to the registered version.

Fixed a problem in the external registration routine.  The external reg
flagfile was not being created.  This has furthered been enhanced in that
PCBVerify will delete the external reg flagfile itself whenever necessary.

Also, added the ability to handle comments in the .CNF file -- PCBVerify will
now stop reading a line of the config file when it hits the first ";".
Everything after the ; will be assumed to be a comment.

This version was never actually released.

-- 4.03 --

Fixed a problem reading the config file identifier.  4.02 would not properly
read the first line of the config file (identifier) and reported that the
version of the config file was pre-4.0.

-- 4.02 --

Fixed the DOORSYS program distributed with 4.00/4.01 which would always
produce a message stating the command line parameters even if you had
given it both filenames.

Changed some of the startup code in PCBVerify to allow for a more tolerant
first line of the config file (now searches for a "4.0" without checking
for the remaing zero.  Also, when the startup code began it would sometimes
appear to lock the system up because the opening message regarding an improper
config file would get erased by other internal routines before the operator
had a chance to see the message.

Added HISTORY.DOC to the ZIPfile to allow tracking of all bug fixes.

-- 4.01 --

4.01 fixes two problems.  First, on PCBoard 14.x systems without the /NETWORK
switch, an error 52 (bad file name) was given.  This version corrects this
problem.  This was due to a null string being passed to the open file routine.

Documentation clarifications were made.  PCBV40.DOC included the callerid
file but UPGRADE.DOC failed to mention it.

----------

If you have trouble with PCBVerify, don't hesitate to call Premier
BBS and ask for help.  I will help anyone who asks and will always do whatever
it takes to get PCBVerify running on your system.  Please do not call me at
home.  Leave a message on the board and I'll respond within 24 hours.

[phone] (2400bps -- rings down to 588-9425)
[phone] (14400 bps, v.32bis)